As a minimum you need the following fields:
Unique_ID (This field is required for a WIP table in an ODBC-compliant database such as SQL, Oracle and DB2 but is not required for WIP stored as xBase files. If you are migrating from a prior version, such as 10.0 to 10.1 (patch 445) or 10.2 (patch 36) or higher, be sure to include this entry in your DFD files, since the system checks for its presence.)
Key1
Key2
KeyID
RecType
CreateTime
OrigUser
CurrUser
ModifyTime
FormSetID
TranCode
StatusCode
FromUser
FromTime
ToUser
ToTime
Desc
InUse
ArcKey
AppData
RecNum
| Note | Never remove any field from the standard WIP file definition. Never rename any field in a WIP DFD file. Doing so can cause damage to your system and can hinder Support’s efforts to solve the problems you will encounter. |
Key1, Key2, and KeyID can be called something different but the other fields must use the names shown in this list. You can add additional items if necessary—just make sure you have the fields shown here.
The only reason to add new fields is if you can place values in the new fields. And only then, if the values are actually going to be used in some manner—either displayed on WIP windows or transferred with the WIP to Archive upon completion.
There are several ways to get nonstandard field values mapped into WIP records:
From the GenWIP program —mapped from the fields in the MANUAL.BCH file when kicking form sets to WIP
By using DAL functions to store the WIP field values during form set editing
Using hooks to write custom code to store the values into the WIP record.
© Copyright 2016, Oracle and/or its affiliates. All rights reserved. Legal notices.